Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

e2e test case: basic send *and receive* #139

Merged
merged 5 commits into from
Nov 22, 2023

Conversation

feuGeneA
Copy link
Contributor

No description provided.

Copy link
Contributor

@cam-schultz cam-schultz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two high level requests

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's hold off on deleting the bash integration tests for now. We're still deciding if there are reasonable use cases for them that the Ginkgo framework can't replicate.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would agree here, lets leave the bash scripts. If we decide to remove, we can create a separate issue to remove them altogether.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed in 98deca9

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After the message is delivered from B->A, can you have the relayer redeem the reward marked in the receipt? That behavior is not currently covered by any of the existing E2E tests.

Copy link

@minghinmatthewlam minghinmatthewlam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just Cam's comment #139 (comment) for redeeming rewards and checking the reward amount is correct

// TODO: figure out why the following is reverting with message
// "execution reverted: TeleporterMessenger: no reward to redeem"
transaction, err := subnetATeleporterMessenger.RedeemRelayerRewards(
&bind.TransactOpts{}, fundedAddress,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should use mockTokenAddress instead of fundedAddress. The parameter of redeemRelayerRewards is the fee asset contract to redeem the rewards for, with the "redeemer" address being the caller of the method. So we should be sure this transaction is being sent from the account specified by the relayer as the reward redeemer, and specify the mock token as the asset being redeemed.

@feuGeneA feuGeneA force-pushed the e2e-basic-send-receive-ginkgo branch from 3034b20 to 92f938a Compare November 22, 2023 01:58
@feuGeneA feuGeneA force-pushed the e2e-basic-send-receive-ginkgo branch from 92f938a to e66a8d4 Compare November 22, 2023 17:51
Copy link
Contributor

@cam-schultz cam-schultz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@feuGeneA feuGeneA merged commit f2f5694 into general-e2e Nov 22, 2023
@geoff-vball geoff-vball deleted the e2e-basic-send-receive-ginkgo branch December 13, 2023 18:04
0xchainlover pushed a commit to avalabsorg/teleporter that referenced this pull request Aug 1, 2024
0xchainlover pushed a commit to avalabsorg/teleporter that referenced this pull request Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants